[教程] 如何在fydeos/openfyde上替换6.6内核

求助答疑
135

哦哦，我还以为你说的是chromebook呢）） :joy:是的，能正常启动
自适应大法好）能用就行（雾）

137

Im having this exact issue idk how to bypass it. @Su12 does your brunch works on FydeOS v18 for n100 boxes?

138

Try enable dev mode and disable root verification as the updated steps say. It should work for n100.

139

Thats how the system is. Enabled Devb and rootfs Disabled. - Let me recheck this…

image

image
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

140

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.

141

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 :eyes:

142

@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

tip：fydeos v18.1已修复

144

我也母鸡啊 :cry:

145

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)

146

想问问这段命令起什么作用？这段命令适用于v17之前的fydeos吗？

147

v18的surface在u盘不会自动挂efi, 这段即使输了也对17的没影响

148

Yo yo yo Monoco Sensei…

20240519_130301
20240519_1303011920×2560 170 KB

Check this out !

149

更换内核后似乎android上的代理软件无法正常的代理chromium（不太确定），v2rayng的日志里看不到走了代理的信息且chromium无法正常访问网站，android上倒是可以正常访问

150

大佬，在FydeOS_for_PC_v18.0-SP1在测试，升级了6.6内核成功，也成功安装到本地硬盘分区中。但有个问题出现，就是手写笔出现连笔问题，就是不仅手写时有笔迹，抬起来离屏幕很近时也会有连着的笔迹出现，要抬很远才不会有笔迹。再测试了一下，没有升级6.6内核之前手写笔写字和画画完全正常。请问一下，有没有办法解决一下呢？

151

大神，你好！最近发现个问题，就是插上耳机后，不仅耳机有声音，外放也还是有声音，不会自动禁止。请问一下，有解决方法吗？

152

1
1815×637 53.1 KB

大佬！我没有在硬盘装这个系统，先用U盘写入v17.1。
然后进入U盘启动-进入画面-按照您的指令一步一步来。
2
21631×787 94.3 KB

第二步。
3
31717×1007 157 KB

第三步。
4
41867×845 138 KB

第四步。
5
51851×881 119 KB

所有工作都完成。
6
6737×391 106 KB

最后点击重启，再次用U盘启动的时候就黑屏了。
7

问题：
版本-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盘在左上脚有一个白杠一闪一闪的，屏幕是黑屏。
是不是我那个步骤出错了？

153

大神，你帮我看下，根据您的文档进行操作的。
是不是我哪里出错了呢》

154

FydeOS for PC v17.1升级内核及解决ESSX8336声卡驱动及音量问题.docx (411.7 KB)
根据前面大神这个教程一步一步操作。

我的是17.1版本，是不是也要执行一下下面的两组操作？

**v18:

  1. https://fydeos.com/question/enable-developer-mode/
  2. 重启
  3. https://fydeos.com/docs/knowledge-base/getting-started/disable-rootfs-verification/
  4. 再重启

8
81391×801 154 KB

操作是这组指令
我没有装硬盘，直接在U盘启动系统的。
手动重启，现在直接黑屏，开机选U盘启动，黑屏

155

我不是大神哦，LZ提供修改的内核才是大神。
我看了一下，你操作的对的啊！重启开机是不是要多等一段时间看看呢？
我自己之后重新整理了那个文档，分开v18和v17的，两个版本上我都试过可以的。在U盘开始运行时最好选择建立本地账户运行试试，至少我看到有人说U盘上操作时v18要用本地账户，安装到硬盘上后可以用Fydeos账户的，v17不存在此问题。

FydeOS for PC v17.1与v18.x升级内核及解决ESSX8336声卡驱动及音量问题.docx (391.8 KB)

对了，我用的镜像写入U盘的软件不是BalenaEtcher，我用的是Rufus，推荐用这个软件。

156

换内核就是有风险的，就可能不能启动，v17不用那些操作，自带了