rp king-rk3399官方固件无法启动redroid:10.0.0-latest，好像在audio过程中就重启了，adb也无法连接
lanlingw opened this issue · 10 comments
Describe the bug
请详细描述问题（ZH_CN）
A clear and concise description of what the bug is.
rp king-rk3399官方固件无法启动redroid:10.0.0-latest，好像在audio过程中就重启了，adb也无法连接
make sure the required kernel modules present
确保必须的内核功能已开启（ZH_CN）
-
grep binder /proc/filesystems -
grep ashmem /proc/misc(optional)
[Wed Nov 22 09:21:20 2023] init: Command 'restart vendor.audio-hal-4-0-msd' action=onrestart (<Service 'audioserver' onrestart>:2) took 0ms and failed: service vendor.audio-hal-4-0-msd not found
[Wed Nov 22 09:21:20 2023] init: Command 'restart audio-hal-2-0' action=onrestart (<Service 'audioserver' onrestart>:3) took 0ms and failed: service audio-hal-2-0 not found
Check dmesg.txt, netd cannot boot:
[Wed Nov 22 09:21:20 2023] init: Service 'netd' (pid 3993) exited with status 1
check logcat.txt, some kernel features are not available:
3980:11-22 01:21:17.546 3993 3993 I netd : Enabling bandwidth control: 92.1ms
3981:11-22 01:21:17.547 3993 3993 E Netd : Error adding IPv6 rule: Address family not supported by protocol
3982:11-22 01:21:17.547 3993 3993 E netd : Failed to initialize RouteController (Address family not supported by protocol)
3983:11-22 01:21:17.547 3993 3993 I netd : Initializing RouteController: 0.6ms
3984:11-22 01:21:17.547 3993 3993 D XfrmController: XfrmController::ipSecAddXfrmInterface, line=1379
3985:11-22 01:21:17.553 3993 3993 D XfrmController: XfrmController::ipSecRemoveTunnelInterface, line=1592
3986:11-22 01:21:17.553 3993 3993 D XfrmController: deviceName=ipsec_test
3987:11-22 01:21:17.553 3993 3993 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHSA
3988:11-22 01:21:17.553 3993 3993 D XfrmController: Sending Netlink XFRM Message: XFRM_MSG_FLUSHPOLICY
3989:11-22 01:21:17.553 3993 3993 I netd : Initializing XfrmController: 6.2ms
3990:11-22 01:21:17.559 3993 3993 E Netd : Unable to create netlink socket for family 5: Protocol not supported
3991:11-22 01:21:17.559 3993 3993 W Netd : Unable to open qlog quota socket, check if xt_quota2 can send via UeventHandler
3992:11-22 01:21:17.565 3993 3993 E Netd : Unable to create netlink socket for family 12: Protocol not supported
3993:11-22 01:21:17.565 3993 3993 E Netd : Unable to open strict socket
3994:11-22 01:21:17.571 3993 3993 E Netd : Unable to create NFLogListener: Status[code: 93, msg: "[Protocol not supported] : socket() failed"]
您这边能指导一下需要哪些内核模块功能吗，是IPV6相关的模块吗
redroid-debug.jpzhScTR.zip
我添加上去内核模块了，netd已经不再崩溃重启，但是还是连接不上
Your redroid container boots succeeded.
Check logcat.txt:
09-20 08:50:07.025 635 1714 D NetworkMonitor/100: PROBE_DNS connectivitycheck.gstatic.com 11ms FAIL
09-20 08:50:07.025 635 1713 D NetworkMonitor/100: PROBE_DNS www.google.com 11ms FAIL
09-20 08:50:07.033 635 1714 D NetworkMonitor/100: PROBE_HTTP http://connectivitycheck.gstatic.com/generate_204 Probe failed with exception java.net.UnknownHostException: Unable to resolve host "connectivitycheck.gstatic.com": No address associated with hostname
09-20 08:50:07.034 635 1713 D NetworkMonitor/100: PROBE_HTTPS https://www.google.com/generate_204 Probe failed with exception java.net.UnknownHostException: Unable to resolve host "www.google.com": No address associated with hostname
09-20 08:50:07.045 635 1712 D NetworkMonitor/100: PROBE_FALLBACK http://play.googleapis.com/generate_204 Probe failed with exception java.net.UnknownHostException: Unable to resolve host "play.googleapis.com": No address associated with hostname
09-20 08:50:07.047 635 1712 D NetworkMonitor/100: isCaptivePortal: isSuccessful()=false isPortal()=false RedirectUrl=null isPartialConnectivity()=false Time=36ms
redroid use 8.8.8.8 as default DNS server, try change to something else if cannot be accessed. And try probe another link if Google related links cannot be accessed.
Have fun~~
启动容器后网络是正常的可以ping通宿主机，等服务启动过后一段时间网络就不正常了，无法ping通127以外的任何地址，不知道是哪里的问题
redroid-debug.hLnSWh2r.zip
Your container network is disabled since probe failed. It's a built-in network feature of Android.
Can the board access 8.8.8.8?
是可以通的，从init进程过渡到其他服务就网络就不可用了，我看了下实时日志打印，好像是都没有启动到网络功能哪里就不可用了，包括使用代理都不行，同网络下的x86平台就可以正常启动
网络模式使用host就无法启动，容器运行后立马停止
Should NEVER try host network mode. Otherwise, your host networking will be messed up.
主要是桥接网络就不正常