Help regarding anbox

I installed anbox using this guide Ultimate Guide to install Anbox in any Arch-based distro(especially Garuda)

I followed all the instructions correctly, but anbox is not starting. neither from terminal nor from GUI

Terminal start

╭─[email protected] in ~ as 🧙 took 3s
╰─λ anbox wait-ready

╭─[email protected] in ~ as 🧙 took 30s
[🔴] ×

when I run this:
sudo ls -1 /dev/binderfs
output:

binder-control
features

this is the output of anbox system-info

╭─[email protected] in ~ took 16ms
╰─λ anbox system-info
version: local-7a0bee7
cpu:
arch:  x86
brand: 12th Gen Intel(R) Core(TM) i5-1235U
features:
- aes
- sse4_1
- sse4_2
- avx
- avx2
os:
name: Garuda Linux
version:
snap-based: false
kernel:
version: Linux version 6.1.6-zen1-2-zen ([email protected]) (gcc (GCC) 12.2.1 20230111, GNU ld (GNU Binutils) 2.40) #1 ZEN SMP PREEMPT_DYNAMIC Mon, 16 Jan 2023 14:55:29 +0000
binder: false
binderfs: true
ashmem: true
graphics:
egl:
vendor: Mesa Project
version: 1.5
extensions:
- EGL_ANDROID_blob_cache
- EGL_ANDROID_native_fence_sync
- EGL_CHROMIUM_sync_control
- EGL_ANGLE_sync_control_rate
- EGL_EXT_buffer_age
- EGL_EXT_create_context_robustness
- EGL_EXT_image_dma_buf_import
- EGL_EXT_image_dma_buf_import_modifiers
- EGL_EXT_swap_buffers_with_damage
- EGL_IMG_context_priority
- EGL_KHR_cl_event2
- EGL_KHR_config_attribs
- EGL_KHR_context_flush_control
- EGL_KHR_create_context
- EGL_KHR_create_context_no_error
- EGL_KHR_fence_sync
- EGL_KHR_get_all_proc_addresses
- EGL_KHR_gl_colorspace
- EGL_KHR_gl_renderbuffer_image
- EGL_KHR_gl_texture_2D_image
- EGL_KHR_gl_texture_3D_image
- EGL_KHR_gl_texture_cubemap_image
- EGL_KHR_image
- EGL_KHR_image_base
- EGL_KHR_image_pixmap
- EGL_KHR_no_config_context
- EGL_KHR_reusable_sync
- EGL_KHR_surfaceless_context
- EGL_KHR_swap_buffers_with_damage
- EGL_EXT_pixel_format_float
- EGL_KHR_wait_sync
- EGL_MESA_configless_context
- EGL_MESA_drm_image
- EGL_MESA_image_dma_buf_export
- EGL_MESA_query_driver
- EGL_NOK_texture_from_pixmap
- EGL_WL_bind_wayland_display
gles2:
vendor: Intel
vendor: OpenGL ES 3.2 Mesa 22.3.3
extensions:
- GL_EXT_blend_minmax
- GL_EXT_multi_draw_arrays
- GL_EXT_texture_filter_anisotropic
- GL_EXT_texture_compression_s3tc
- GL_EXT_texture_compression_dxt1
- GL_EXT_texture_compression_rgtc
- GL_EXT_texture_format_BGRA8888
- GL_OES_compressed_ETC1_RGB8_texture
- GL_OES_depth24
- GL_OES_element_index_uint
- GL_OES_fbo_render_mipmap
- GL_OES_mapbuffer
- GL_OES_rgb8_rgba8
- GL_OES_standard_derivatives
- GL_OES_stencil8
- GL_OES_texture_3D
- GL_OES_texture_float
- GL_OES_texture_float_linear
- GL_OES_texture_half_float
- GL_OES_texture_half_float_linear
- GL_OES_texture_npot
- GL_OES_vertex_half_float
- GL_EXT_draw_instanced
- GL_EXT_texture_sRGB_decode
- GL_OES_EGL_image
- GL_OES_depth_texture
- GL_AMD_performance_monitor
- GL_OES_packed_depth_stencil
- GL_EXT_texture_type_2_10_10_10_REV
- GL_NV_conditional_render
- GL_OES_get_program_binary
- GL_APPLE_texture_max_level
- GL_EXT_discard_framebuffer
- GL_EXT_read_format_bgra
- GL_NV_pack_subimage
- GL_EXT_frag_depth
- GL_NV_fbo_color_attachments
- GL_OES_EGL_image_external
- GL_OES_EGL_sync
- GL_OES_vertex_array_object
- GL_OES_viewport_array
- GL_ANGLE_pack_reverse_row_order
- GL_ANGLE_texture_compression_dxt3
- GL_ANGLE_texture_compression_dxt5
- GL_EXT_occlusion_query_boolean
- GL_EXT_robustness
- GL_EXT_texture_rg
- GL_EXT_unpack_subimage
- GL_NV_draw_buffers
- GL_NV_read_buffer
- GL_NV_read_depth
- GL_NV_read_depth_stencil
- GL_NV_read_stencil
- GL_EXT_draw_buffers
- GL_EXT_map_buffer_range
- GL_KHR_debug
- GL_KHR_robustness
- GL_KHR_texture_compression_astc_ldr
- GL_NV_pixel_buffer_object
- GL_OES_depth_texture_cube_map
- GL_OES_required_internalformat
- GL_OES_surfaceless_context
- GL_EXT_color_buffer_float
- GL_EXT_debug_label
- GL_EXT_sRGB_write_control
- GL_EXT_separate_shader_objects
- GL_EXT_shader_framebuffer_fetch
- GL_EXT_shader_group_vote
- GL_EXT_shader_implicit_conversions
- GL_EXT_shader_integer_mix
- GL_EXT_tessellation_point_size
- GL_EXT_tessellation_shader
- GL_INTEL_conservative_rasterization
- GL_INTEL_performance_query
- GL_ANDROID_extension_pack_es31a
- GL_EXT_base_instance
- GL_EXT_compressed_ETC1_RGB8_sub_texture
- GL_EXT_copy_image
- GL_EXT_draw_buffers_indexed
- GL_EXT_draw_elements_base_vertex
- GL_EXT_gpu_shader5
- GL_EXT_polygon_offset_clamp
- GL_EXT_primitive_bounding_box
- GL_EXT_render_snorm
- GL_EXT_shader_io_blocks
- GL_EXT_texture_border_clamp
- GL_EXT_texture_buffer
- GL_EXT_texture_cube_map_array
- GL_EXT_texture_norm16
- GL_EXT_texture_view
- GL_KHR_blend_equation_advanced
- GL_KHR_blend_equation_advanced_coherent
- GL_KHR_context_flush_control
- GL_KHR_robust_buffer_access_behavior
- GL_NV_image_formats
- GL_NV_shader_noperspective_interpolation
- GL_OES_copy_image
- GL_OES_draw_buffers_indexed
- GL_OES_draw_elements_base_vertex
- GL_OES_gpu_shader5
- GL_OES_primitive_bounding_box
- GL_OES_sample_shading
- GL_OES_sample_variables
- GL_OES_shader_io_blocks
- GL_OES_shader_multisample_interpolation
- GL_OES_tessellation_point_size
- GL_OES_tessellation_shader
- GL_OES_texture_border_clamp
- GL_OES_texture_buffer
- GL_OES_texture_cube_map_array
- GL_OES_texture_stencil8
- GL_OES_texture_storage_multisample_2d_array
- GL_OES_texture_view
- GL_EXT_blend_func_extended
- GL_EXT_buffer_storage
- GL_EXT_float_blend
- GL_EXT_geometry_point_size
- GL_EXT_geometry_shader
- GL_EXT_shader_samples_identical
- GL_EXT_texture_sRGB_R8
- GL_KHR_no_error
- GL_KHR_texture_compression_astc_sliced_3d
- GL_NV_fragment_shader_interlock
- GL_OES_EGL_image_external_essl3
- GL_OES_geometry_point_size
- GL_OES_geometry_shader
- GL_OES_shader_image_atomic
- GL_EXT_clear_texture
- GL_EXT_clip_cull_distance
- GL_EXT_disjoint_timer_query
- GL_EXT_texture_compression_s3tc_srgb
- GL_MESA_shader_integer_functions
- GL_EXT_clip_control
- GL_EXT_color_buffer_half_float
- GL_EXT_memory_object
- GL_EXT_memory_object_fd
- GL_EXT_semaphore
- GL_EXT_semaphore_fd
- GL_EXT_texture_compression_bptc
- GL_EXT_texture_mirror_clamp_to_edge
- GL_KHR_parallel_shader_compile
- GL_EXT_EGL_image_storage
- GL_EXT_shader_framebuffer_fetch_non_coherent
- GL_EXT_texture_shadow_lod
- GL_INTEL_blackhole_render
- GL_MESA_framebuffer_flip_y
- GL_NV_compute_shader_derivatives
- GL_EXT_demote_to_helper_invocation
- GL_EXT_depth_clamp
- GL_EXT_texture_query_lod
- GL_MESA_bgra
╭─[email protected] in ~ as 🧙 took 40ms
╰─λ anbox check-features
Your computer does meet all requirements to run Anbox
╭─[email protected] in ~ as 🧙 took 19ms
╰─λ garuda-inxi
System:
Kernel: 6.1.6-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=5db7243d-174d-446d-8935-c049889ff0f7 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: HP product: HP Laptop 15s-fq5xxx v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: HP model: 8A20 v: 20.18 serial: <superuser required> UEFI: AMI
v: F.16 date: 09/15/2022
Battery:
ID-1: BAT0 charge: 24.9 Wh (59.4%) condition: 41.9/41.0 Wh (102.0%)
volts: 11.5 min: 11.4 model: HP Primary type: Li-ion serial: <filter>
status: discharging cycles: 59
CPU:
Info: model: 12th Gen Intel Core i5-1235U bits: 64 type: MST AMCP
arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
microcode: 0x424
Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled
cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB
L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 1037 high: 2500 min/max: 400/4400:3300 scaling:
driver: intel_pstate governor: powersave cores: 1: 864 2: 501 3: 860 4: 945
5: 873 6: 1200 7: 605 8: 1279 9: 914 10: 999 11: 2500 12: 913
bogomips: 59904
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics]
vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-12.2
process: Intel 10nm built: 2021-22+ ports: active: eDP-1 empty: DP-1,
DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46a8
class-ID: 0300
Device-2: Quanta HP TrueVision HD Camera type: USB driver: uvcvideo
bus-ID: 1-3:2 chip-ID: 0408:536c class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x153b built: 2020 res: 1920x1080
hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Graphics (ADL GT2)
direct render: Yes
Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio
vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:51c8 class-ID: 0401
Sound API: ALSA v: k6.1.6-zen1-2-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw_8822ce v: N/A modules: rtw88_8822ce
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0
chip-ID: 10ec:c822 class-ID: 0280
IF: wlo1 state: up mac: <filter>
IF-ID-1: anbox0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IF-ID-2: vethTCNR6b state: up speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-10:3 chip-ID: 0bda:b00c class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 2 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 476.94 GiB used: 61.05 GiB (12.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNU512GZH
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: HPS1 temp: 27.9 C scheme: GPT
Partition:
ID-1: / raw-size: 56.59 GiB size: 56.59 GiB (100.00%)
used: 29.47 GiB (52.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 612 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p8 maj-min: 259:8
ID-3: /home raw-size: 119.27 GiB size: 119.27 GiB (100.00%)
used: 31.58 GiB (26.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-4: /var/log raw-size: 56.59 GiB size: 56.59 GiB (100.00%)
used: 29.47 GiB (52.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-5: /var/tmp raw-size: 56.59 GiB size: 56.59 GiB (100.00%)
used: 29.47 GiB (52.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 7.44 GiB used: 236 MiB (3.1%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 349 Uptime: 2h 25m wakeups: 3083 Memory: 7.44 GiB
used: 4.03 GiB (54.2%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1570
libs: 495 tools: pamac,paru,yay Shell: fish v: 3.6.0 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.24
Garuda (2.6.14-1):
System install date:     2022-12-07
Last full system update: 2023-01-18
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Please help me

1 Like

Missing your garuda-inxi.

2 Likes

I have edited the post. Now does this look good?

1 Like

https://aur.archlinux.org/packages/anbox-modules-dkms#comment-846854

sudo modprobe binder_linux devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder

sudo modprobe ashmem_linux

sudo umount  /dev/binderfs

sudo mount -t binder none /dev/binderfs

Now again post:
sudo ls -1 /dev/binderfs

Does this get it working, @ameyjoshi3068 ?

I had exams the last two days so I couldn't reply.

1 Like

It looks like anbox-module-dkms cannot install binder for my machine

╭─[email protected] in ~ as 🧙 took 408ms
[🔴] × sudo pacman -S anbox-modules-dkms
warning: anbox-modules-dkms-5.19-4.1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) anbox-modules-dkms-5.19-4.1

Total Download Size:   0.08 MiB
Total Installed Size:  0.48 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
anbox-modules-dkms-5.19-4.1-x86_64     78.1 KiB  85.9 KiB/s 00:01 [------------------------------------] 100%
(1/1) checking keys in keyring                                     [------------------------------------] 100%
(1/1) checking package integrity                                   [------------------------------------] 100%
(1/1) loading package files                                        [------------------------------------] 100%
(1/1) checking for file conflicts                                  [------------------------------------] 100%
(1/1) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/2) Performing snapper pre snapshots for the following configurations...
==> root: 179
(2/2) Remove upgraded DKMS modules
==> dkms remove --no-depmod ashmem/1 -k 6.1.6-zen1-2-zen
==> dkms remove binder/1
:: Processing package changes...
(1/1) reinstalling anbox-modules-dkms                              [------------------------------------] 100%
==>> Building & Installing Modules (binder)
make -C /lib/modules/6.1.6-zen1-2-zen/build V=0 M=$PWD
make[1]: Entering directory '/usr/lib/modules/6.1.6-zen1-2-zen/build'
CC [M]  /tmp/binder_install/deps.o
In file included from ././include/linux/kconfig.h:5,
from <command-line>:
./include/generated/autoconf.h:4400: warning: "CONFIG_ANDROID_BINDER_DEVICES" redefined
4400 | #define CONFIG_ANDROID_BINDER_DEVICES ""
|
<command-line>: note: this is the location of the previous definition
./include/generated/autoconf.h:5760: warning: "CONFIG_ANDROID_BINDERFS" redefined
5760 | #define CONFIG_ANDROID_BINDERFS 1
|
<command-line>: note: this is the location of the previous definition
/tmp/binder_install/deps.c: In function ‘close_fd_get_file’:
/tmp/binder_install/deps.c:92:42: error: ‘res’ undeclared (first use in this function)
92 |         return close_fd_get_file_ptr(fd, res);
|                                          ^~~
/tmp/binder_install/deps.c:92:42: note: each undeclared identifier is reported only once for each function it appears in
/tmp/binder_install/deps.c:92:16: error: too many arguments to function ‘close_fd_get_file_ptr’
92 |         return close_fd_get_file_ptr(fd, res);
|                ^~~~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:250: /tmp/binder_install/deps.o] Error 1
make[1]: *** [Makefile:1990: /tmp/binder_install] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.1.6-zen1-2-zen/build'
make: *** [Makefile:8: all] Error 2
cp binder_linux.ko /usr/src/binder-1/
cp: cannot stat 'binder_linux.ko': No such file or directory
make: *** [Makefile:11: install] Error 1
==>> Building & Installing Modules (ashmem)
make -C /lib/modules/6.1.6-zen1-2-zen/build V=0 M=$PWD
make[1]: Entering directory '/usr/lib/modules/6.1.6-zen1-2-zen/build'
CC [M]  /tmp/ashmem_install/deps.o
CC [M]  /tmp/ashmem_install/ashmem.o
LD [M]  /tmp/ashmem_install/ashmem_linux.o
MODPOST /tmp/ashmem_install/Module.symvers
CC [M]  /tmp/ashmem_install/ashmem_linux.mod.o
LD [M]  /tmp/ashmem_install/ashmem_linux.ko
BTF [M] /tmp/ashmem_install/ashmem_linux.ko
make[1]: Leaving directory '/usr/lib/modules/6.1.6-zen1-2-zen/build'
cp ashmem_linux.ko /usr/src/ashmem-1/
==>> Cleaning Up
==>> Loading Anbox Modules
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/6.1.6-zen1-2-zen
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-anbox.preset: 'default'
-> -k /boot/vmlinuz-linux-xanmod-anbox -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-anbox.img
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.1.5-x64v1-xanmod1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-xanmod-anbox.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 260: popd: directory stack empty
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-anbox.preset: 'fallback'
-> -k /boot/vmlinuz-linux-xanmod-anbox -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-anbox-fallback.img -S autodetect
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.1.5-x64v1-xanmod1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-xanmod-anbox-fallback.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 260: popd: directory stack empty
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.1.6-zen1-2-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 260: popd: directory stack empty
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.1.6-zen1-2-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 260: popd: directory stack empty
==> Image generation successful
:: Running post-transaction hooks...
(1/8) Arming ConditionNeedsUpdate...
(2/8) Install DKMS modules
==> dkms install --no-depmod binder/1 -k 6.1.6-zen1-2-zen
Error! Bad return status for module build on kernel: 6.1.6-zen1-2-zen (x86_64)
Consult /var/lib/dkms/binder/1/build/make.log for more information.
==> WARNING: `dkms install --no-depmod binder/1 -k 6.1.6-zen1-2-zen' exited 10
==> dkms install --no-depmod ashmem/1 -k 6.1.6-zen1-2-zen
==> depmod 6.1.6-zen1-2-zen
(3/8) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-anbox.preset: 'default'
-> -k /boot/vmlinuz-linux-xanmod-anbox -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-anbox.img
==> Starting build: 6.1.5-x64v1-xanmod1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-xanmod-anbox.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-anbox.preset: 'fallback'
-> -k /boot/vmlinuz-linux-xanmod-anbox -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-anbox-fallback.img -S autodetect
==> Starting build: 6.1.5-x64v1-xanmod1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-xanmod-anbox-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 6.1.6-zen1-2-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 6.1.6-zen1-2-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful
(4/8) Foreign/AUR package notification
python-bluetooth-battery 1.3.2-4
rootactions-servicemenu 2.7.3-1
(5/8) Orphaned package notification...
debugedit 5.0-4
geocode-glib 3.26.4-2
libvisual 0.4.0-8
maven 3.8.7-1
mcfly 0.7.1-1
(6/8) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/default/grub.pacnew
/etc/pamac.conf.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
Please check and merge
(7/8) Performing snapper post snapshots for the following configurations...
==> root: 180
(8/8) Syncing all file systems...

╭─[email protected] in ~ as 🧙 took 1m45s
╰─λ sudo modprobe binder_linux devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/6.1.6-zen1-2-zen

But it looks like ashem and binder are loaded

╭─[email protected] in ~
╰─λ grep binder /proc/filesystems
grep ashmem /proc/misc
nodev   binder
123 ashmem

here is the output you asked for

╭─[email protected] in ~
╰─λ sudo ls -1 /dev/binderfs
[sudo] password for amey:
binder-control
features

Possibly related (I don't use Anbox): see latest comment here:
https://aur.archlinux.org/packages/anbox-modules-dkms#comment-897829
Related to this:

Seems to be fixed, so should be hopefully committed soon.

4 Likes

You could btw check out Waydroid, we have a guide for that too in the forum.
But first you would have to undo all the changes you have made for Anbox, including removing Anbox modules.
Waydroid is actively being developed and is supposed to be the successor of Anbox.

Edit:
I just checked out, anbox was last active 4 months ago, while Waydroid was last contributed to just 4 hours ago!
:sweat_smile:

5 Likes

I will check Waydroid for sure. Thanks, everyone for helping me

1 Like