不是，miix510 i5-6200u，除了摄像头没驱动其他都挺好的））
？（表述有误，抱歉）
我意思是你的机器用的是 Chromebook 6.6内核吗？（我的surface 3用surface 6.6的内核启动不了安卓）
哦哦，我还以为你说的是chromebook呢）） 
是的，能正常启动
自适应大法好）能用就行（雾）
行，那我周末再用Chromebook 6.6内核试一遍，看看能不能正常启动
Im having this exact issue idk how to bypass it. @Su12 does your brunch works on FydeOS v18 for n100 boxes?
Try enable dev mode and disable root verification as the updated steps say. It should work for n100.
Thats how the system is. Enabled Devb and rootfs Disabled. - Let me recheck this…
Got it right. Any chances u mention… a few advantages of this? Is it more closer to the ChromeOS in terms of Android sub System? Steam will work etc?
Im gonna try to follow it here @Su12 if you allow me: https://community.fydeos.io/t/topic/29373/1
I am still able to edit your post as administrator. There are some disinformation translated, I can edit for you if you don’t mind.
Feel free 100% no problem. Keep us updated too on the other side. If you make the post yourself there I will be happy to delete mine. I ask myself why u didnt you lazy sloth 
@Su12 发现了个神奇现象
在另一台电脑上试了surface-6.6的内核，竟然可以启用安卓子系统！（用chromebook-6.6的内核也正常）
但从surface3启动换好surface-6.6内核的U盘，却不能启动安卓子系统，看了下arc.log
在启用安卓子系统时，这段报错 log 一直在循环
2024-04-04T10:33:48.920129Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.vibrator@1.0::IVibrator/default
2024-04-04T10:33:48.920441Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.vibrator@1.0::IVibrator/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:48.920463Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.vibrator@1.0::IVibrator/default
2024-04-04T10:33:48.923205Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.vibrator@1.0::IVibrator/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:48.923249Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.vibrator@1.0::IVibrator/default
2024-04-04T10:33:48.927317Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.ir@1.0::IConsumerIr/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:48.928088Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.ir@1.0::IConsumerIr/default
2024-04-04T10:33:48.994129Z INFO arc-kmsg-logger[4269]: init: processing action (sys.sysctl.extra_free_kbytes=*) from (/init.rc:726)
2024-04-04T10:33:49.002088Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.vr@1.0::IVr/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.005706Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.vr@1.0::IVr/default
2024-04-04T10:33:49.085341Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.oemlock@1.0::IOemLock/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.085648Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.oemlock@1.0::IOemLock/default
2024-04-04T10:33:49.296787Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.thermal@1.0::IThermal/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.296925Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.thermal@1.0::IThermal/default
2024-04-04T10:33:49.315222Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.contexthub@1.0::IContexthub/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.315277Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.contexthub@1.0::IContexthub/default
2024-04-04T10:33:49.359962Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.weaver@1.0::IWeaver/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.360296Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.weaver@1.0::IWeaver/default
2024-04-04T10:33:49.363154Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘android.hardware.authsecret@1.0::IAuthSecret/default’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:49.363286Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface android.hardware.authsecret@1.0::IAuthSecret/default
2024-04-04T10:33:50.284136Z INFO arc-kmsg-logger[4269]: init: Received control message ‘interface_start’ for ‘hardware.google.media.c2@1.0::IComponentStore/software’ from pid: 7 (/system/bin/hwservicemanager)
2024-04-04T10:33:50.284191Z ERR arc-kmsg-logger[4269]: init: Could not find service hosting interface hardware.google.media.c2@1.0::IComponentStore/software
2024-04-04T10:33:51.107898Z INFO arc-kmsg-logger[4269]: init: Service ‘vendor.camera-provider-2-4’ (pid 1131) exited with status 1
2024-04-04T10:33:51.107969Z INFO arc-kmsg-logger[4269]: init: Sending signal 9 to service ‘vendor.camera-provider-2-4’ (pid 1131) process group…
2024-04-04T10:33:51.108175Z INFO arc-kmsg-logger[4269]: libprocessgroup: Successfully killed process cgroup uid 1047 pid 1131 in 0ms
2024-04-04T10:33:51.110644Z INFO arc-kmsg-logger[4269]: init: starting service ‘vendor.camera-provider-2-4’…
2024-04-04T10:33:51.112634Z ERR arc-kmsg-logger[4269]: init: couldn’t write 1496 to /dev/cpuset/camera-daemon/tasks: No such file or directory
2024-04-04T10:33:51.112698Z ERR arc-kmsg-logger[4269]: init: failed to set pid 1496 ioprio=1,4: Operation not permitted
2024-04-04T10:33:56.592461Z INFO arc-kmsg-logger[4269]: init: Service ‘vendor.camera-provider-2-4’ (pid 1496) exited with status 1
2024-04-04T10:33:56.592568Z INFO arc-kmsg-logger[4269]: init: Sending signal 9 to service ‘vendor.camera-provider-2-4’ (pid 1496) process group…
2024-04-04T10:33:56.592692Z INFO arc-kmsg-logger[4269]: libprocessgroup: Successfully killed process cgroup uid 1047 pid 1496 in 0ms
2024-04-04T10:33:56.595443Z INFO arc-kmsg-logger[4269]: init: starting service ‘vendor.camera-provider-2-4’…
2024-04-04T10:33:56.598061Z ERR arc-kmsg-logger[4269]: init: couldn’t write 1502 to /dev/cpuset/camera-daemon/tasks: No such file or directory
2024-04-04T10:33:56.598109Z ERR arc-kmsg-logger[4269]: init: failed to set pid 1502 ioprio=1,4: Operation not permitted
所以…是我这台surface3的问题？可是之前在v17换内核安卓就没问题啊？
看来是 fydeos v18 与 Intel Atom 处理器的问题，等v19吧 dT-Tb
我也母鸡啊 
With Fyde18 we lost the ability to make priviledge containers on penguin.
Any idea if there is any work-around it?
“Error: Invalid config: LXD was configured to only allow unprivileged containers”
Simply put … I cant enable the dam seb’os boxes for steam to boot.
(ARM64 edge2 tales)
想问问这段命令起什么作用？这段命令适用于v17之前的fydeos吗？
v18的surface在u盘不会自动挂efi, 这段即使输了也对17的没影响
更换内核后似乎android上的代理软件无法正常的代理chromium（不太确定），v2rayng的日志里看不到走了代理的信息且chromium无法正常访问网站，android上倒是可以正常访问
大佬，在FydeOS_for_PC_v18.0-SP1在测试，升级了6.6内核成功，也成功安装到本地硬盘分区中。但有个问题出现，就是手写笔出现连笔问题，就是不仅手写时有笔迹，抬起来离屏幕很近时也会有连着的笔迹出现，要抬很远才不会有笔迹。再测试了一下，没有升级6.6内核之前手写笔写字和画画完全正常。请问一下，有没有办法解决一下呢？
大神，你好！最近发现个问题，就是插上耳机后，不仅耳机有声音，外放也还是有声音，不会自动禁止。请问一下，有解决方法吗？
大佬！我没有在硬盘装这个系统，先用U盘写入v17.1。
然后进入U盘启动-进入画面-按照您的指令一步一步来。
第二步。
第三步。
第四步。
所有工作都完成。
最后点击重启，再次用U盘启动的时候就黑屏了。
问题：
版本-FydeOS for PC v17.1
下载文件：chromebook-6.6.tar.gz
下载文件：firmware.tar.gz
将文件复制到FydeOS的“我的文件“-下载内容”目录中，也即/home/chronos/user/Downloads路径里。
FydeOS的U盘启动盘启动进行试用，进入FydeOS桌面，按Ctrl+Alt+T键进入shell模式。
输入shell进入终端命令提示符。按下面步骤操作：
sudo -i
mount -oremount,rw /
rm -rf /lib/modules/*
rm -rf /lib/firmware
cd /home/chronos/user/Downloads
tar -xvf chromebook-6.6.tar.gz -C /
tar -xvf firmware.tar.gz -C /
cp /vmlinux /tmp/grub_mnt/syslinux/vmlinuz.A
#cp /vmlinux /tmp/grub_mnt/syslinux/vmlinuz.B
cp /vmlinux /boot/vmlinuz
最后需要输入什么吗？
我直接在系统上点击重启了，但是重启之后就无法再通过U盘进入系统了，进入U盘在左上脚有一个白杠一闪一闪的，屏幕是黑屏。
是不是我那个步骤出错了？