主题 : tiny4412 + android 5启动失败。请教思路 Operation not supported on transport endpoint 复制链接 | 浏览器收藏 | 打印
级别: 新手上路
UID: 128745
精华: 0
发帖: 3
金钱: 15 两
威望: 3 点
贡献值: 0 点
综合积分: 6 分
注册时间: 2016-10-23
最后登录: 2016-11-18
楼主  发表于: 2016-11-17 15:51

 tiny4412 + android 5启动失败。请教思路 Operation not supported on transport endpoint

我最近在测试android 5 。tiny4412.  使用nfs文件系统启动,启动后显示类似信息,lcd显示安卓图标就一直停在那里。



[    7.242846] link_reset() speed: 100 duplex: 1
[    7.255112] IP-Config: Complete:
[    7.255150]      device=eth0, addr=192.168.0.180, mask=255.255.255.0, gw=192.168.0.1,
[    7.255234]      host=arm, domain=, nis-domain=(none),
[    7.255289]      bootserver=192.168.0.110, rootserver=192.168.0.110, rootpath=
[    7.257005] hotplug_policy_init: intialised with policy : DVFS_NR_BASED_HOTPLUG
[    7.273558] VFS: Mounted root (nfs filesystem) on device 0:13.
[    7.273662] Freeing init memory: 240K
[    8.281148] init: /dev/hw_random not found
[    8.488026] MFC F/W loaded successfully (size: 376448)
[    9.357924] init: /dev/hw_random not found
[    9.393339] SELinux: Could not set context for /cache:  Operation not supported on transport endpoint
[    9.396880] SELinux: Could not set context for /cache/lost+found:  Operation not supported on transport endpoint
[    9.467933] SELinux: Could not set context for /data:  Operation not supported on transport endpoint
[   10.775139] SELinux: Could not set context for /data:  Operation not supported on transport endpoint
[   10.782608] SELinux: Could not set context for /data/nativebenchmark:  Operation not supported on transport endpoint
[   10.785382] SELinux: Could not set context for /data/nativebenchmark/binderAddInts:  Operation not supported on transport endpoint
[   10.785555] SELinux: Could not set context for /data/gps:  Operation not supported on transport endpoint
[   10.795464] SELinux: Could not set context for /data/local:  Operation not supported on transport endpoint
[   10.805118] SELinux: Could not set context for /data/local/tmp:  Operation not supported on transport endpoint
[   10.815217] SELinux: Could not set context for /data/dontpanic:  Operation not supported on transport endpoint
[   10.825087] SELinux: Could not set context for /data/ethernet:  Operation not supported on transport endpoint
[   10.835833] SELinux: Could not set context for /data/ethernet/ethernet.conf:  Operation not supported on transport endpoint
[   10.844325] SELinux: Could not set context for /data/security:  Operation not supported on transport endpoint
[   10.855963] SELinux: Could not set context for /data/app-private:  Operation not supported on transport endpoint
[   10.866080] SELinux: Could not set context for /data/property:  Operation not supported on transport endpoint
[   10.875955] SELinux: Could not set context for /data/mediadrm:  Operation not supported on transport endpoint
[   10.885967] SELinux: Could not set context for /data/resource-cache:  Operation not supported on transport endpoint
[   10.896343] SELinux: Could not set context for /data/app-lib:  Operation not supported on transport endpoint
[   10.906089] SELinux: Could not set context for /data/bugreports:  Operation not supported on transport endpoint
[   10.914472] SELinux: Could not set context for /data/drm:  Operation not supported on transport endpoint
[   10.925826] SELinux: Could not set context for /data/app-asec:  Operation not supported on transport endpoint
[   10.935575] SELinux: Could not set context for /data/app:  Operation not supported on transport endpoint
[   10.944955] SELinux: Could not set context for /data/data:  Operation not supported on transport endpoint
[   10.952876] SELinux: Could not set context for /data/lost+found:  Operation not supported on transport endpoint
[   10.964716] SELinux: Could not set context for /data/nativetest:  Operation not supported on transport endpoint
[   10.976724] SELinux: Could not set context for /data/nativetest/clatd_test:  Operation not supported on transport endpoint
[   10.986742] SELinux: Could not set context for /data/nativetest/clatd_test/clatd_test:  Operation not supported on transport endpoint
[   10.996006] SELinux: Could not set context for /data/nativetest/backtrace_test:  Operation not supported on transport endpoint
[   11.009999] SELinux: Could not set context for /data/nativetest/backtrace_test/backtrace_test:  Operation not supported on transport endpoint
[   11.020025] SELinux: Could not set context for /data/media:  Operation not supported on transport endpoint
[   11.031455] SELinux: Could not set context for /data/misc:  Operation not supported on transport endpoint
[   11.041636] SELinux: Could not set context for /data/misc/bluetooth:  Operation not supported on transport endpoint
[   11.051333] SELinux: Could not set context for /data/misc/user:  Operation not supported on transport endpoint
[   11.061344] SELinux: Could not set context for /data/misc/radio:  Operation not supported on transport endpoint
[   11.071467] SELinux: Could not set context for /data/misc/bluedroid:  Operation not supported on transport endpoint
[   11.081859] SELinux: Could not set context for /data/misc/ethernet:  Operation not supported on transport endpoint
[   11.092330] SELinux: Could not set context for /data/misc/sms:  Operation not supported on transport endpoint
[   11.102081] SELinux: Could not set context for /data/misc/wifi:  Operation not supported on transport endpoint
[   11.112127] SELinux: Could not set context for /data/misc/wifi/wpa_supplicant:  Operation not supported on transport endpoint
[   11.123351] SELinux: Could not set context for /data/misc/wifi/sockets:  Operation not supported on transport endpoint
[   11.133974] SELinux: Could not set context for /data/misc/shared_relro:  Operation not supported on transport endpoint
[   11.144838] SELinux: Could not set context for /data/misc/keystore:  Operation not supported on transport endpoint
[   11.155093] SELinux: Could not set context for /data/misc/vpn:  Operation not supported on transport endpoint
[   11.164955] SELinux: Could not set context for /data/misc/net:  Operation not supported on transport endpoint
[   11.174830] SELinux: Could not set context for /data/misc/adb:  Operation not supported on transport endpoint
[   11.184839] SELinux: Could not set context for /data/misc/keychain:  Operation not supported on transport endpoint
[   11.195216] SELinux: Could not set context for /data/misc/systemkeys:  Operation not supported on transport endpoint
[   11.205585] SELinux: Could not set context for /data/misc/media:  Operation not supported on transport endpoint
[   11.215739] SELinux: Could not set context for /data/misc/zoneinfo:  Operation not supported on transport endpoint
[   11.225988] SELinux: Could not set context for /data/misc/dhcp:  Operation not supported on transport endpoint
[   11.235992] SELinux: Could not set context for /data/dalvik-cache:  Operation not supported on transport endpoint
[   11.246287] SELinux: Could not set context for /data/dalvik-cache/profiles:  Operation not supported on transport endpoint
[   11.476330] init: Warning!  Service lmkd needs a SELinux domain defined; please fix!
[   11.494701] init: Warning!  Service servicemanager needs a SELinux domain defined; please fix!
[   11.675433] init: Warning!  Service vold needs a SELinux domain defined; please fix!
[   11.833108] init: Warning!  Service surfaceflinger needs a SELinux domain defined; please fix!
[   11.904632] init: cannot find '/system/bin/setup_fs', disabling 'setup_fs'
[   12.001065] binder: 1687:1687 transaction failed 29189, size 0-0
[   12.033150] init: property 'ro.serialno' doesn't exist while expanding '${ro.serialno}'
[   12.033294] init: cannot expand '${ro.serialno}' while writing to '/sys/class/android_usb/android0/iSerial'
[   12.707363] adb_open
[   12.707679] DUN is registerd
[   12.707743] adb_bind_config
[   13.001440] binder: 1687:1687 transaction failed 29189, size 0-0
[   14.025087] healthd: wakealarm_init: timerfd_create failed
[   14.025339] healthd: No charger supplies found
[   14.025398] healthd: No battery devices found
shell@tiny4412:/ $ [   16.467859] s3c-fimc3: FIMC3 1 opened.
[   16.739088] FriendlyARM http://www.arm9.net
[   16.862122] asoc: wm8960-hifi <-> samsung-i2s.0 mapping ok
[   16.863165] asoc: wm8960-hifi <-> samsung-i2s.4 mapping ok
[   16.968416] [HPD_IF] s5p_hpd_ioctl: HPD status is unplugged
[   16.970165] type=1400 audit(1388586329.275:51): avc: denied { call } for pid=1693 comm="sechdmiservice" scontext=u:r:surfaceflinger:s0 tcontext=u:r:init:s0 tclass=binder
[   17.285576] type=1400 audit(1388586329.280:52): avc: denied { transfer } for pid=1693 comm="sechdmiservice" scontext=u:r:surfaceflinger:s0 tcontext=u:r:init:s0 tclass=binder
[   17.285837] type=1400 audit(1388586329.280:53): avc: denied { getattr } for pid=1689 comm="servicemanager" scontext=u:r:init:s0 tcontext=u:r:surfaceflinger:s0 tclass=process
[   17.294569] type=1400 audit(1388586329.520:54): avc: denied { create } for pid=1725 comm="vold" name="179:0" scontext=u:r:init:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file
[   18.320319] s3c-usbgadget s3c-usbgadget: usb phy usage(22)
[   18.320439] s3c-usbgadget s3c-usbgadget: Already power on PHY
[   19.597653] usbcore: registered new interface driver rtl8192cu
[   20.041517] type=1400 audit(1388586332.350:55): avc: denied { call } for pid=1691 comm="surfaceflinger" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=binder
[   20.042345] type=1400 audit(1388586332.350:56): avc: denied { transfer } for pid=1689 comm="servicemanager" scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=binder
[   20.042979] s3c-fimc3: FIMC3 2 opened.
[   20.816410] init: Warning!  Service bootanim needs a SELinux domain defined; please fix!
[   21.057461] RTL871X: rtl8188eu driver version=v4.1.5_7309.20130425
[   21.057532] RTL871X: build time: May 27 2015 14:36:10
[   21.058092] usbcore: registered new interface driver rtl8188eu





请教是哪方面引起的?
级别: 新手上路
UID: 132192
精华: 0
发帖: 3
金钱: 15 两
威望: 3 点
贡献值: 0 点
综合积分: 6 分
注册时间: 2017-04-23
最后登录: 2017-09-22
1楼  发表于: 2017-09-04 21:21
请问决解了没?我也遇到这个问题
^很多问题的背后都是简单的原因......
级别: 荣誉会员
UID: 34780
精华: 0
发帖: 1219
金钱: 6230 两
威望: 1246 点
贡献值: 0 点
综合积分: 2438 分
注册时间: 2010-12-21
最后登录: 2017-09-18
2楼  发表于: 2017-09-06 11:07
Android 5启用了 SELinux, 如果使用 NFS 则会存在权限方面的问题,不建议采用 NFS
级别: 新手上路
UID: 132192
精华: 0
发帖: 3
金钱: 15 两
威望: 3 点
贡献值: 0 点
综合积分: 6 分
注册时间: 2017-04-23
最后登录: 2017-09-22
3楼  发表于: 2017-09-08 16:12

 回 2楼(911gt3) 的帖子

修改android后,每次都要重新刷系统,好麻烦!请问除了使用NFS,还有其他的方便的方法吗?
^很多问题的背后都是简单的原因......
级别: 荣誉会员
UID: 34780
精华: 0
发帖: 1219
金钱: 6230 两
威望: 1246 点
贡献值: 0 点
综合积分: 2438 分
注册时间: 2010-12-21
最后登录: 2017-09-18
4楼  发表于: 2017-09-18 19:37
改动不大的话可以用 adb sync ; 如果改动比较多,还是建议重新刷比较可靠