You are not logged in.

#1 2022-12-11 14:02:38

T-Dynamos
Member
From: India
Registered: 2022-07-19
Posts: 8

anbox-modules-dkms : does not install successfully

Error:

(7/7) installing anbox-modules-dkms                [#################] 100%
==>> Building & Installing Modules (binder)
make -C /lib/modules/6.0.7-arch1-1/build V=0 M=$PWD
make[1]: *** /lib/modules/6.0.7-arch1-1/build: No such file or directory.  Stop.
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.0.7-arch1-1/build V=0 M=$PWD
make[1]: *** /lib/modules/6.0.7-arch1-1/build: No such file or directory.  Stop.
make: *** [Makefile:12: all] Error 2
cp ashmem_linux.ko /usr/src/ashmem-1/
cp: cannot stat 'ashmem_linux.ko': No such file or directory
make: *** [Makefile:15: install] Error 1
==>> Cleaning Up
==>> Loading Anbox Modules
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/6.0.7-arch1-1
modprobe: FATAL: Module ashmem_linux not found in directory /lib/modules/6.0.7-arch1-1
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.0.7-arch1-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: [fsck]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 257: popd: directory stack empty
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
==> Starting build: 6.0.7-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: qla1280
==> 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: [fsck]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux-fallback.img
pushd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
/usr/bin/mkinitcpio: line 257: popd: directory stack empty
==> Image generation successful
:: Running post-transaction hooks...
(1/7) Reloading system manager configuration...
(2/7) Creating temporary files...
(3/7) Reloading device manager configuration...
(4/7) Arming ConditionNeedsUpdate...
(5/7) Install DKMS modules
==> ERROR: Missing slim.png kernel headers for module ashmem/1.
==> ERROR: Missing media kernel headers for module binder/1.
==> ERROR: Missing opt kernel headers for module ashmem/1.
==> ERROR: Missing version kernel headers for module ashmem/1.
==> ERROR: Missing data kernel headers for module ashmem/1.
==> ERROR: Missing sbin kernel headers for module binder/1.
==> ERROR: Missing home kernel headers for module ashmem/1.
==> ERROR: Missing lost+found kernel headers for module ashmem/1.
==> ERROR: Missing var kernel headers for module ashmem/1.
==> ERROR: Missing data kernel headers for module binder/1.
==> ERROR: Missing etc kernel headers for module binder/1.
==> ERROR: Missing var kernel headers for module binder/1.
==> ERROR: Missing mnt kernel headers for module binder/1.
==> ERROR: Missing home kernel headers for module binder/1.
==> ERROR: Missing proc kernel headers for module binder/1.
==> ERROR: Missing dev kernel headers for module ashmem/1.
==> ERROR: Missing usr kernel headers for module binder/1.
==> ERROR: Missing usr kernel headers for module ashmem/1.
==> ERROR: Missing opt kernel headers for module binder/1.
==> ERROR: Missing dev kernel headers for module binder/1.
==> ERROR: Missing etc kernel headers for module ashmem/1.
==> ERROR: Missing media kernel headers for module ashmem/1.
==> ERROR: Missing srv kernel headers for module binder/1.
==> ERROR: Missing sys kernel headers for module binder/1.
==> ERROR: Missing tmp kernel headers for module ashmem/1.
==> ERROR: Missing lib kernel headers for module binder/1.
==> ERROR: Missing proc kernel headers for module ashmem/1.
==> ERROR: Missing lib kernel headers for module ashmem/1.
==> ERROR: Missing run kernel headers for module ashmem/1.
==> ERROR: Missing srv kernel headers for module ashmem/1.
==> ERROR: Missing boot kernel headers for module ashmem/1.
==> ERROR: Missing lost+found kernel headers for module binder/1.
==> ERROR: Missing bin kernel headers for module binder/1.
==> ERROR: Missing lib64 kernel headers for module binder/1.
==> ERROR: Missing bin kernel headers for module ashmem/1.
==> ERROR: Missing run kernel headers for module binder/1.
==> ERROR: Missing mnt kernel headers for module ashmem/1.
==> ERROR: Missing boot kernel headers for module binder/1.
==> ERROR: Missing root kernel headers for module ashmem/1.
==> ERROR: Missing lib64 kernel headers for module ashmem/1.
==> ERROR: Missing slim.png kernel headers for module binder/1.
==> ERROR: Missing sys kernel headers for module ashmem/1.
==> ERROR: Missing sbin kernel headers for module ashmem/1.
==> ERROR: Missing root kernel headers for module binder/1.
==> ERROR: Missing version kernel headers for module binder/1.
==> ERROR: Missing tmp kernel headers for module binder/1.
(6/7) Updating executables in /usr/bin...
(7/7) Updating the desktop file MIME type cache...


Just wondering in world of linux

Offline

#2 2022-12-11 14:18:51

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: anbox-modules-dkms : does not install successfully

When you installed dkms, it told you some optional deps. Do you have the headers installed for your kernel?

Offline

#3 2022-12-11 14:37:19

T-Dynamos
Member
From: India
Registered: 2022-07-19
Posts: 8

Re: anbox-modules-dkms : does not install successfully

Do I need to install core/linux-headers   ?
Does not works even after installing

Last edited by T-Dynamos (2022-12-11 14:43:52)


Just wondering in world of linux

Offline

#4 2022-12-11 16:42:20

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,267

Re: anbox-modules-dkms : does not install successfully

Your kernel is outdated, if you installed linux-headers now it would be matching 6.0.12 and you'd need to boot that

Offline

#5 2024-03-03 13:54:37

ckristin
Member
Registered: 2024-03-03
Posts: 1

Re: anbox-modules-dkms : does not install successfully

i just install linux-headers package in pacman to solved this problem

Offline

Board footer

Powered by FluxBB