website: fix symbol

This commit is contained in:
tiann
2023-01-26 11:50:15 +08:00
parent da38815ce0
commit 2ebb363350
4 changed files with 15 additions and 4 deletions

View File

@@ -5,7 +5,9 @@ First, you should read the Android Official docs for kernel build:
1. [Building Kernels](https://source.android.com/docs/setup/build/building-kernels) 1. [Building Kernels](https://source.android.com/docs/setup/build/building-kernels)
2. [GKI Release Builds](https://source.android.com/docs/core/architecture/kernel/gki-release-builds) 2. [GKI Release Builds](https://source.android.com/docs/core/architecture/kernel/gki-release-builds)
> This page is for GKI devices, if you use an old kernel, please refer [how to integrate KernelSU for old kernel](how-to-integrate-for-non-gki) ::: warning
This page is for GKI devices, if you use an old kernel, please refer [how to integrate KernelSU for old kernel](how-to-integrate-for-non-gki)
:::
## Build Kernel ## Build Kernel

View File

@@ -35,6 +35,11 @@ If you find that KPROBES is still not activated, you can try enabling `CONFIG_MO
But if you encounter a boot loop when integrated KernelSU, it is maybe *kprobe is broken in your kernel*, you should fix the kprobe bug or use the second way. But if you encounter a boot loop when integrated KernelSU, it is maybe *kprobe is broken in your kernel*, you should fix the kprobe bug or use the second way.
:::tip How to check if kprobe is broken
comment out `ksu_enable_sucompat()` and `ksu_enable_ksud()` in `KernelSU/kernel/ksu.c`, the the device boot normally, then kprobe may be broken.
:::
## Manully modify the kernel source ## Manully modify the kernel source
If kprobe can not work in your kernel (maybe a upstream bug or kernel below 4.8), then you can try this way: If kprobe can not work in your kernel (maybe a upstream bug or kernel below 4.8), then you can try this way:

View File

@@ -5,7 +5,9 @@
1. [构建内核](https://source.android.com/docs/setup/build/building-kernels) 1. [构建内核](https://source.android.com/docs/setup/build/building-kernels)
2. [通用内核映像 (GKI) 发布构建](https://source.android.com/docs/core/architecture/kernel/gki-release-builds) 2. [通用内核映像 (GKI) 发布构建](https://source.android.com/docs/core/architecture/kernel/gki-release-builds)
> 本文档适用于 GKI 设备,如果你是旧内核,请参考[如何为非GKI设备集成 KernelSU](how-to-integrate-for-non-gki) ::: warning
本文档适用于 GKI 设备,如果你是旧内核,请参考[如何为非GKI设备集成 KernelSU](how-to-integrate-for-non-gki)
:::
## 构建内核 ## 构建内核

View File

@@ -35,8 +35,10 @@ CONFIG_KPROBE_EVENTS=y
如果你在集成 KernelSU 之后手机无法启动,那么很可能你的内核中 **kprobe 工作不正常**,你需要修复这个 bug 或者用第二种方法。 如果你在集成 KernelSU 之后手机无法启动,那么很可能你的内核中 **kprobe 工作不正常**,你需要修复这个 bug 或者用第二种方法。
> 如何验证是否是 kprobe 的问题? :::tip 如何验证是否是 kprobe 的问题?
> 注释掉 `KernelSU/kernel/ksu.c` 中 `enable_sucompat()`,如果正常开机,那么就是 kprobe 的问题;或者你可以手动尝试使用 kprobe 功能,如果不正常,手机会直接重启。
注释掉 `KernelSU/kernel/ksu.c``ksu_enable_sucompat()``ksu_enable_ksud()`,如果正常开机,那么就是 kprobe 的问题;或者你可以手动尝试使用 kprobe 功能,如果不正常,手机会直接重启。
:::
## 手动修改内核源码 ## 手动修改内核源码