diff --git a/website/docs/guide/how-to-integrate-for-non-gki.md b/website/docs/guide/how-to-integrate-for-non-gki.md index 45baf954..b35ef382 100644 --- a/website/docs/guide/how-to-integrate-for-non-gki.md +++ b/website/docs/guide/how-to-integrate-for-non-gki.md @@ -31,6 +31,8 @@ CONFIG_KPROBE_EVENTS=y And build your kernel again, KernelSU should works well. +If you find that KPROBES is still not activated, you can try enabling `CONFIG_MODULES`. (If it still doesn't take effect, use `make menuconfig` to search for other dependencies of KPROBES) + 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. ## Manully modify the kernel source diff --git a/website/docs/id_ID/guide/how-to-integrate-for-non-gki.md b/website/docs/id_ID/guide/how-to-integrate-for-non-gki.md index 231be77d..27b91cbf 100644 --- a/website/docs/id_ID/guide/how-to-integrate-for-non-gki.md +++ b/website/docs/id_ID/guide/how-to-integrate-for-non-gki.md @@ -31,6 +31,8 @@ CONFIG_KPROBE_EVENTS=y Dan build kernel Anda lagi, KernelSU seharusnya bekerja dengan baik. +Jika Anda menemukan bahwa KPROBES masih belum diaktifkan, Anda dapat mencoba mengaktifkan `CONFIG_MODULES`. (Jika masih belum berlaku, gunakan `make menuconfig` untuk mencari ketergantungan KPROBES yang lain) + etapi jika Anda mengalami boot loop saat mengintegrasikan KernelSU, itu mungkin *kprobe rusak di kernel Anda*, Anda harus memperbaiki bug kprobe atau menggunakan cara kedua. ## Memodifikasi sumber kernel secara manual diff --git a/website/docs/vi_VN/guide/how-to-integrate-for-non-gki.md b/website/docs/vi_VN/guide/how-to-integrate-for-non-gki.md index f8b39ca2..7bda2a60 100644 --- a/website/docs/vi_VN/guide/how-to-integrate-for-non-gki.md +++ b/website/docs/vi_VN/guide/how-to-integrate-for-non-gki.md @@ -32,6 +32,8 @@ CONFIG_KPROBE_EVENTS=y Rồi build lại kernel của bạn, KernelSU sẽ hoạt động ok. +Nếu bạn thấy rằng KPROBES vẫn chưa được kích hoạt, bạn có thể thử bật `CONFIG_MODULES`. (Nếu nó vẫn không có hiệu lực, hãy sử dụng `make menuconfig` để tìm kiếm các phần phụ thuộc khác của KPROBES) + Nhưng nếu bạn gặp bootloop khi tích hợp KernelSU thì có thể *kprobe bị hỏng trong kernel*, bạn nên fix lỗi kprobe trong mã nguồn hoặc dùng cách 2. ## Chỉnh sửa mã nguồn kernel thủ công diff --git a/website/docs/zh_CN/guide/how-to-integrate-for-non-gki.md b/website/docs/zh_CN/guide/how-to-integrate-for-non-gki.md index 9e93a4d2..9304f0f0 100644 --- a/website/docs/zh_CN/guide/how-to-integrate-for-non-gki.md +++ b/website/docs/zh_CN/guide/how-to-integrate-for-non-gki.md @@ -31,6 +31,8 @@ CONFIG_KPROBE_EVENTS=y 最后，重新编译你的内核即可。 +如果你发现KPROBES仍未生效，很有可能是因为它的依赖项`CONFIG_MODULES`没有被启用（如果还是未生效请键入`make menuconfig`搜索KPROBES 的其它依赖并启用 ） + 如果你在集成 KernelSU 之后手机无法启动，那么很可能你的内核中 **kprobe 工作不正常**，你需要修复这个 bug 或者用第二种方法。 > 如何验证是否是 kprobe 的问题？