Glad to hear that!

 

This is still a workaround. You already put all needed libs under your application and it should find all them by default, without the workaround. We have to continue to check it for a thorough solution when we are free.

 

Yanmin

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Tuesday, July 30, 2019 1:32 PM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: Tan, Ming <ming.tan@intel.com>; Gaurav Gupta <gaurav@trainingdata.io>; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>; celadon@lists.01.org
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Yanmin,

 

    thank you for all your help. this worked , I am able to push the libraries.txt file and deployed the app and it loaded the library.

 

    07-30 04:31:47.873  4016  4016 I System.out: INTELMSDK ....... loading .... start ..

07-30 04:31:47.891  4016  4016 I libva   : VA-API version 1.2.0
07-30 04:31:47.891  4016  4016 I libva   : va_getDriverName() returns 0
07-30 04:31:47.891  4016  4016 I libva   : Trying to open /vendor/lib64//i965_drv_video.so
07-30 04:31:47.895  4016  4016 I viewoverlaytest: type=1400 audit(0.0:81): avc: denied { execute } for path="/vendor/lib64/libgmm_umd.so" dev="sda11" ino=104 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
07-30 04:31:47.906  4016  4016 I libva   : Found init function __vaDriverInit_1_2
07-30 04:31:47.911  4016  4016 I libva   : va_openDriver() returns 0
07-30 04:31:47.911  4016  4016 D media-jni: MediaJni: JNI_OnLoad ++
07-30 04:31:47.911  4016  4016 I System.out: INTELMSDK ....... loading .... done ..

 

Thanks,

Sathish

   

 

On Tue, Jul 30, 2019 at 5:41 AM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Did you run below commands?

adb root

adb remount

 

 

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Tuesday, July 30, 2019 3:19 AM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: Tan, Ming <ming.tan@intel.com>; Gaurav Gupta <gaurav@trainingdata.io>; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>; celadon@lists.01.org
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

I tried userdebug.

TARGET_BUILD_VARIANT=userdebug

 

All the below steps are successful , but the mount failed.

 

Installer.efi flashing unlock
Installer.efi continue

adb disable-verity
     sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july27$ adb disable-verity
      Successfully disabled verity
      Now reboot your device for settings to take effect
adb reboot
It went to recovery mode, I choose factory reset
.

 

But the adb remount of the vendor partition failed with error " not user mountable in fstab".

 

1|celadon:/vendor/etc $ cat /proc/mounts | grep vendor                                                                                        
/dev/block/pci/pci0000:00/0000:00:17.0//by-name/vendor_a /vendor ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,acl 0 0
/dev/block/by-name/config /mnt/vendor/oem_config ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic 0 0
/dev/block/by-name/factory /vendor/factory ext4 rw,seclabel,noatime 0 0
celadon:/vendor/etc $
celadon:/vendor/etc $
1|celadon:/vendor/etc $
mount -o rw,remount /dev/block/pci/pci0000:00/0000:00:17.0//by-name/vendor_a /vendor                                                          <
mount: '/dev/block/pci/pci0000:00/0000:00:17.0//by-name/vendor_a' not user mountable in fstab

1|celadon:/vendor/etc $ 

 

Thanks,

Sathish

 

On Mon, Jul 29, 2019 at 8:12 AM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Can you try user-debug?

 

From: Tan, Ming
Sent: Monday, July 29, 2019 10:26 AM
To: Zhang, Yanmin <yanmin.zhang@intel.com>; Gaurav Gupta <gaurav@trainingdata.io>; Sathish <satish.chevuru@gmail.com>
Cc: Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>
Subject: RE: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Are you using KBL NUC 7i7BNH?

It does not support USB device mode, then does not support fastboot.

 

BR/Tan Ming.

 

From: Zhang, Yanmin
Sent: Monday, July 29, 2019 8:22 AM
To: Gaurav Gupta <gaurav@trainingdata.io>; Sathish <satish.chevuru@gmail.com>
Cc: Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>; Tan, Ming <ming.tan@intel.com>
Subject: RE: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

I use user-debug at lunch before compiling.

 

+Ming.

 

From: Gaurav Gupta [mailto:gaurav@trainingdata.io]
Sent: Sunday, July 28, 2019 12:02 AM
To: Sathish <satish.chevuru@gmail.com>
Cc: Zhang, Yanmin <yanmin.zhang@intel.com>; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Hi Yanmin,

 

My experience with disable-verity on NUC6i5SYK was similar.

After disable-verity showed success status, there was an error "Fastboot mode failed: Unsupported"

 

On Sat, Jul 27, 2019 at 8:22 AM Sathish <satish.chevuru@gmail.com> wrote:

I have tried power off and on again and it still says "Fastboot mode failed".

 

I have recorded a video of my steps I executed and attached the drive link.

 

I started with clean install and proceeded with the steps.

 

1) Installed the Celadon Image using startup.nsh and booted into the android home

2) Plugged in the USB and executed unlock commands

3) It went into recovery mode and I selected factory data reset.

4) After booting up , I connected to the device and executed disable-verity and reboot.

5) It gave me the "Fastboot mode failed: Unsupported"

6) I restarted the device ( power off and on ) and again it tried booting and got to "Fastboot mode failed: Unsupported"

 

I am using the celadon eng build.

 

 

Thanks,

Sathish

 

On Thu, Jul 25, 2019 at 6:01 AM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Can you try to power off and on the NUC? I also use NUC7i7BNH.

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Thursday, July 25, 2019 2:50 AM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>; Gaurav Gupta <gaurav@trainingdata.io>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Yanmin,

 

Unlocked worked, disable verity worked , but the adb reboot after it failed.

 

sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb disable-verity
Successfully disabled verity
Now reboot your device for settings to take effect
sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb reboot

 

I see the below error now and the boot stopped.

 

Fastboot mode failed: Unsupported.

 

I am using NUC7i7BNH , Is this because of the NUC type.

 

Thanks,

Sathish

 

 

On Wed, Jul 24, 2019 at 11:01 AM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Plug the install usb key, enter UEFI shell, and run:

Installer.efi flashing unlock

Installer.efi continue

 

Then, it would be unlocked.

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Wednesday, July 24, 2019 1:28 PM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: celadon@lists.01.org; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

 

 

It says device unlocked.

 

sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb disable-verity
Device is locked. Please unlock the device first

 

The device is already enabled for developer options and OEM is also unlocked.

 

Thanks,

Sathish

 

On Wed, Jul 24, 2019 at 9:24 AM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

adb disable-verity

adb reboot

It might boot to recovery mode, then you need choose reset factory

adb remount

Then, push the file and change anything.

 

From: Sathish [mailto:satish.chevuru@gmail.com]
Sent: Wednesday, July 24, 2019 11:50 AM
To: Zhang, Yanmin <yanmin.zhang@intel.com>
Cc: celadon@lists.01.org; Chen, Tianmi <tianmi.chen@intel.com>; Cao, Jenny Q <jenny.q.cao@intel.com>; Lin, Johnson <johnson.lin@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Yanmin,

 

I tried this and it says "/vendor/etc" as a read only file system and failed to copy the file.

 

sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb push public.libraries.txt /vendor/etc

adb: error: failed to copy 'public.libraries.txt' to '/vendor/etc/public.libraries.txt': remote couldn't create file: Read-only file system
public.libraries.txt: 0 files pushed. 0.0 MB/s (51 bytes in 0.004s)

 

celadon:/vendor/etc # touch test.txt
touch: 'test.txt': Read-only file system
1|celadon:/vendor/etc # 

 

I earlier bundled all the dependant libraries in the application lib, based on the suggestion from android help link you mentioned above.

 

Thanks,

Sathish

 

 

 

On Tue, Jul 23, 2019 at 12:49 PM Zhang, Yanmin <yanmin.zhang@intel.com> wrote:

Sathish,

 

Since Android N, apk need call official API. All access to private libraries will be blocked.

https://developer.android.com/about/versions/nougat/android-7.0-changes

 

You can work around it by:

1)      Add the shared object file names into a config file:

ymzhang@ymzhang:~/android/data/logs/KBL$ cat public.libraries.txt

i965_drv_video.so

libva.so

libdrm.so

libgmm_umd.so

ymzhang@ymzhang:~/android/data/logs/KBL$ adb push public.libraries.txt /vendor/etc/

 

2)      After booting, run: adb shell setenforce 0

 

You app can start to a red window on my KBL.

 

Yanmin

 

From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Zhang, Yanmin
Sent: Wednesday, July 17, 2019 8:44 AM
To: Sathish <satish.chevuru@gmail.com>; celadon@lists.01.org
Cc: Chen, Tianmi <tianmi.chen@intel.com>; Xiao, Jin <jin.xiao@intel.com>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

+Jin, Tianmi.

 

I remember you raised the similar issue 2 months ago. It seems not resolved.

 

From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Sathish
Sent: Wednesday, July 17, 2019 1:50 AM
To: celadon@lists.01.org
Subject: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file

 

Hi,

 

 I am getting the below error while deploying an application no NUC7i7BNH with celadon PMR.

 

The library is available in the given path, but unable to load the library and reporting not accessible for the namespace error.

 

 E libva   : dlopen of /vendor/lib64//i965_drv_video.so failed: dlopen failed: library "/vendor/lib64//i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"

 

E libva   : dlopen of /system/lib64/i965_drv_video.so failed: dlopen failed: library "/system/lib64/i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"

 

Appreciate your inputs on this.

 

Thanks,

Sathish


 

--

Gaurav,

Co-founder, TrainingData.io

+1-917-386-3396

228 Webster Street,           
Palo Alto,                             

CA, 94301