android/SukiSU-Ultra
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

website: fix symbol

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/guide/how-to-build.md
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)
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

5
website/docs/guide/how-to-integrate-for-non-gki.md
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.
:::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
If kprobe can not work in your kernel (maybe a upstream bug or kernel below 4.8), then you can try this way: