我最近下载了适用于 Android x86 8.1 的 .rpm 包，使用 Alien 将其转换为 .deb，然后安装它（修改后配置脚本以/etc/grub.d/40_custom代替/boot/grub/custom.cfg菜单项）。但是，当它启动时，它会卡在几个失败的任务上。
如果我选择Android x86 8.1GRUB 菜单，它就会卡在带有下划线的屏幕上。如果我选择Android x86 8.1 (DEBUG mode)，它会显示大量错误。使用这两种方法，它都无法进入启动徽标。
以下是其一直循环的日志条目。
[ 669.206600] modprobe: netdev-dummy0
[ 669.206699] type-1400 audit(153301730 956:1730) avc: denied { getattr } for pid=8559 comm="netd" path="/vendor" dev="tmpfs" ino=363 scontext=u:r:netd:s0
[ 669.343896] modprobe: dummy0 [ 672.349605] init: starting service "cameraserver"...
[ 672.343896] init: property_set("ro.boottime.cameraserver", "671915327209") failed: property already set
[ 672.358466] init: couldn't write 8598 to /dev/cpuset/camera-daemon/tasks: No such file or directory
[ 672.702811] init: starting service 'media'...
[ 672.718181] init: property_set("ro.boottime.media, "672275478248") failed: property already set
[ 672.729461] init: couldn't write 8598 to /dev/cpuset/foreground/tasks: No space left on device
[ 672.967430] init: starting service 'surfaceflinger'...
[ 672.984282] init: property_set("ro.boottime.surfaceflinger", "672541344661") failed: property slready set
[ 672.996160] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[ 672.996425] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[ 673.483713] type=1400 audit(1533017035.153:1745): avc: denied { read } for pid=8599 name="vendor" dev="tmpfs" ino=363 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tmpfs:s0 tclass=Ink_file permissive=1
[ 673.552332] type=1400 audit(1533017035.322:1746): avc: denied { read } for pid=8600 comm="system-server-i" name="vendor" dev="tmpfs" ino=363 scontext=u:r:system_server:s0 tcontext=u:object_r:tmpfs:s0 tclass=Ink_file permissive=1
[ 678.578389] type=1400 audit(1533017040.416:1789): avc: denied { open } for pid=8599 comm="surfaceflinger" path="/dev/tty0" dev="tmpfs" ino=7383 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file permissive=1
[ 678.578389] type=1400 audit(1533017040.416:1790): avc: denied { ioctl } for pid=8693 comm="surfaceflinger" path="/dev/tty0" dev="tmpfs" ino=7383 ioctlcmd=0x4b3a scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file permissive=1
[ 678.578530] type=1400 audit(1533017040.416:1790): avc: denied { ioctl } for pid=8693 comm="surfaceflinger" path="/dev/tty0" dev="tmpfs" ino=7383 ioctlcmd=0x4b3a scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file permissive=1
[ 678.578545] type=1400 audit(1533017040.416:1791): avc: denied { sys_tty_config } for pid=8693 comm="surfaceflinger" capability=26 ino=7383 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=capability permissive=1
[ 678.707414] input: Android Power Button as /devices/virtual/input/input27
[ 678.715346] type=1400 audit(1533017040.416:1791): avc: denied { sys_tty_config } for pid=8693 comm="surfaceflinger" capability=26 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=capability permissive=1
[ 678.715356] type=1400 audit(1533017040.546:1792): avc: denied { write } for pid=8694 comm="system_server" name="uinput" dev="tmpfs" ino=8331 scontext=u:r:system_server:s0 tcontext=u:object_r:uhid_device:s0 tclass=chr_file permissive=1
[ 678.852574] binder_alloc: 8694: binder_alloc_buf, no vma
[ 678.861176] 8692:8692 transaction failed 29189/-3, size 88-0 line 3141
[ 679.228876] x_tables: ip_tables: owner match: used from hooks INPUT, but only valid for OUTPUT/POSTROUTING
[ 679.228876] x_tables: ip6_tables: owner match: used from hooks INPUT, but only valid for OUTPUT/POSTROUTING
它开始在屏幕上无限重复这些台词。
我还发现系统登录/android-8.1-rc1/data/log.txt和上传了。
有什么方法可以修复这个问题吗？
我的系统是 HP 10 TS 笔记本电脑（e010nr）（没有硬件变化）。
答案1
我也有同样的问题，你修复了吗？这让我很抓狂，而且这似乎不是每个人在强制使用 VESA 模式时遇到的主要问题，因为我一直在寻找修复方法，这是我经过广泛搜索后找到的唯一列出的完全相同的问题结果。