Announcement

Collapse
No announcement yet.

modprobe ERROR, could not insert ashmem-linux

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    modprobe ERROR, could not insert ashmem-linux

    This module needs to be loaded for anbox to work. I installed anbox from the default ubuntu repository (didn't add any extra repo). The modules are compiled in the kernel, not dkms. Secure boot is enabled.

    I get the message-

    insmod /lib/modules/5.3.0-13-generic/kernel/drivers/staging/android/ashmem_linux.ko
    modprobe: ERROR: could not insert 'ashmem_linux': Operation not permitted

    Any suggestions ?!

    I am running the latest 19.10 updates.
    DISTRIB_ID=Ubuntu
    DISTRIB_RELEASE=19.10
    DISTRIB_CODENAME=eoan
    DISTRIB_DESCRIPTION="Ubuntu Eoan Ermine (development branch)"

    #2
    did you use "sudo" wile trying to insert the module?

    it needs root privilege to do so

    VINNY
    i7 4core HT 8MB L3 2.9GHz
    16GB RAM
    Nvidia GTX 860M 4GB RAM 1152 cuda cores

    Comment


      #3
      look hear https://docs.anbox.io/userguide/install.html

      and hear (this one needs to be done first) https://docs.anbox.io/userguide/inst...l_modules.html

      VINNY
      i7 4core HT 8MB L3 2.9GHz
      16GB RAM
      Nvidia GTX 860M 4GB RAM 1152 cuda cores

      Comment


        #4
        Originally posted by vinnywright View Post
        did you use "sudo" wile trying to insert the module?

        it needs root privilege to do so

        VINNY
        Yes, modprobe run as root.

        Comment


          #5
          Originally posted by vinnywright View Post
          These modules are part of the installed kernel. I did NOT compile the modules. No dkms involved as already stated.

          Comment


            #6
            Not doubting you (as to the modules being 'part of the installed kernel', but what does lsmod report?
            Windows no longer obstruct my view.
            Using Kubuntu Linux since March 23, 2007.
            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

            Comment


              #7
              Originally posted by Snowhog View Post
              Not doubting you (as to the modules being 'part of the installed kernel', but what does lsmod report?
              Module Size Used by
              iptable_mangle 16384 1
              xt_CHECKSUM 16384 1
              iptable_nat 16384 1
              xt_MASQUERADE 20480 1
              nf_nat 40960 2 iptable_nat,xt_MASQUERADE
              nf_conntrack 139264 2 nf_nat,xt_MASQUERADE
              nf_defrag_ipv6 24576 1 nf_conntrack
              nf_defrag_ipv4 16384 1 nf_conntrack
              libcrc32c 16384 2 nf_conntrack,nf_nat
              xt_tcpudp 20480 5
              bridge 176128 0
              stp 16384 1 bridge
              llc 16384 2 bridge,stp
              iptable_filter 16384 1
              bpfilter 32768 0
              ccm 20480 6
              rfcomm 81920 4
              cmac 16384 0
              bnep 24576 2
              uvcvideo 98304 0
              btusb 57344 0
              btrtl 20480 1 btusb
              videobuf2_vmalloc 20480 1 uvcvideo
              btbcm 16384 1 btusb
              videobuf2_memops 20480 1 videobuf2_vmalloc
              btintel 24576 1 btusb
              videobuf2_v4l2 24576 1 uvcvideo
              videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo
              bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
              videodev 208896 3 videobuf2_v4l2,uvcvideo,videobuf2_common
              mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
              ecdh_generic 16384 1 bluetooth
              ecc 28672 1 ecdh_generic
              nls_iso8859_1 16384 1
              snd_hda_codec_realtek 114688 1
              snd_hda_codec_generic 81920 1 snd_hda_codec_realtek
              snd_hda_codec_hdmi 61440 1
              snd_hda_intel 49152 4
              snd_hda_codec 131072 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_i ntel,snd_hda_codec_realtek
              snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_i ntel,snd_hda_codec,snd_hda_codec_realtek
              snd_hwdep 20480 1 snd_hda_codec
              snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd _hda_core
              edac_mce_amd 32768 0
              iwlmvm 401408 0
              snd_seq_midi 20480 0
              kvm_amd 98304 0
              snd_seq_midi_event 16384 1 snd_seq_midi
              ccp 94208 1 kvm_amd
              kvm 643072 1 kvm_amd
              mac80211 851968 1 iwlmvm
              snd_rawmidi 36864 1 snd_seq_midi
              irqbypass 16384 1 kvm
              libarc4 16384 1 mac80211
              input_leds 16384 0
              snd_seq 69632 2 snd_seq_midi,snd_seq_midi_event
              serio_raw 20480 0
              huawei_wmi 16384 0
              wmi_bmof 16384 0
              ledtrig_audio 16384 3 snd_hda_codec_generic,huawei_wmi,snd_hda_codec_rea ltek
              sparse_keymap 16384 1 huawei_wmi
              snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi
              snd_timer 36864 2 snd_seq,snd_pcm
              hid_multitouch 28672 0
              joydev 28672 0
              iwlwifi 348160 1 iwlmvm
              snd 86016 19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_h da_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_code c,snd_hda_cod
              ec_realtek,snd_timer,snd_pcm,snd_rawmidi
              k10temp 16384 0
              cfg80211 712704 3 iwlmvm,iwlwifi,mac80211
              snd_pci_acp3x 16384 0
              soundcore 16384 1 snd
              mac_hid 16384 0
              sch_fq_codel 20480 1
              parport_pc 40960 0
              ppdev 24576 0
              lp 20480 0
              parport 53248 3 parport_pc,lp,ppdev
              ip_tables 32768 3 iptable_filter,iptable_nat,iptable_mangle
              x_tables 40960 6 iptable_filter,xt_tcpudp,xt_CHECKSUM,ip_tables,xt_ MASQUERADE,iptable_mangle
              autofs4 45056 2
              dm_crypt 45056 1
              crct10dif_pclmul 16384 1
              crc32_pclmul 16384 0
              ghash_clmulni_intel 16384 0
              amdgpu 4190208 22
              hid_generic 16384 0
              amd_iommu_v2 20480 1 amdgpu
              gpu_sched 32768 1 amdgpu
              i2c_algo_bit 16384 1 amdgpu
              ttm 106496 1 amdgpu
              aesni_intel 372736 6
              drm_kms_helper 184320 1 amdgpu
              aes_x86_64 20480 1 aesni_intel
              syscopyarea 16384 1 drm_kms_helper
              crypto_simd 16384 1 aesni_intel
              sysfillrect 16384 1 drm_kms_helper
              sysimgblt 16384 1 drm_kms_helper
              ahci 40960 3
              fb_sys_fops 16384 1 drm_kms_helper
              cryptd 24576 3 crypto_simd,ghash_clmulni_intel
              psmouse 155648 0
              drm 491520 11 gpu_sched,drm_kms_helper,amdgpu,ttm
              i2c_piix4 28672 0
              libahci 32768 1 ahci
              glue_helper 16384 1 aesni_intel
              wmi 32768 2 huawei_wmi,wmi_bmof
              i2c_hid 28672 0
              video 49152 0
              hid 126976 3 i2c_hid,hid_multitouch,hid_generic

              Comment


                #8
                Originally posted by Snowhog View Post
                Not doubting you (as to the modules being 'part of the installed kernel', but what does lsmod report?
                not sure how this helps but I included the lsmod output. The module can be found at

                /lib/modules/5.3.0-13-generic/kernel/drivers/staging/android/ashmem_linux.ko

                I didn't compile the kernel and I didn't compile this module separately- it came with the kernel.

                Comment


                  #9
                  You probably need to install the dkms packages in order to compile useable modules for your 5.03 kernel, are you sure that you don't have to still compile modules that will work?
                  Last edited by claydoh; Oct 05, 2019, 09:00 PM.

                  Comment


                    #10
                    Google finds https://github.com/anbox/anbox/issues/1070, and that thread suggests it's a secure boot issue, hence "operation not permitted". Weird, IMO. Have you got secure boot on?
                    Regards, John Little

                    Comment


                      #11
                      He does have secure boot enabled. See his comment in first post.
                      Windows no longer obstruct my view.
                      Using Kubuntu Linux since March 23, 2007.
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                      Comment

                      Working...