在提交问题之前，请先确认以下几点：
- 我已经搜索过现有问题，但没有找到相关内容。
- 我将在KernelSU管理器 - 设置 - 报告日志中上传bug报告文件。
- 我知道如何重现这个问题，这个问题可能不特定于我的设备。
描述问题：驱动程序已在内核级别加载，但管理器显示驱动程序未被检测到。
重现步骤：无法响应
预期行为：无法响应
屏幕截图：
日志信息：
[ 1.122707] KernelSU: Initialized on: 5.4.300-qgki-gba3e74cdbd1a-dirty (aarch64) with driver version: 40201
[ 1.122719] KernelSU: feature: feature management initialized
[ 1.122727] KernelSU: KernelSU IOCTL Commands:
[ 1.122732] KernelSU: GRANT_ROOT = 0x00004b01
[ 1.122737] KernelSU: GET_INFO = 0x80004b02
[ 1.122741] KernelSU: REPORT_EVENT = 0x40004b03
[ 1.122744] KernelSU: SET_SEPOLICY = 0xc0004b04
[ 1.122748] KernelSU: CHECK_SAFEMODE = 0x80004b05
[ 1.122752] KernelSU: GET_ALLOW_LIST = 0xc0004b06
[ 1.122756] KernelSU: GET_DENY_LIST = 0xc0004b07
[ 1.122759] KernelSU: UID_GRANTED_ROOT = 0xc0004b08
[ 1.122764] KernelSU: UID_SHOULD_UMOUNT = 0xc0004b09
[ 1.122767] KernelSU: GET_MANAGER_UID = 0x80004b0a
[ 1.122771] KernelSU: GET_APP_PROFILE = 0xc0004b0b
[ 1.122774] KernelSU: SET_APP_PROFILE = 0x40004b0c
[ 1.122778] KernelSU: GET_FEATURE = 0xc0004b0d
[ 1.122781] KernelSU: SET_FEATURE = 0x40004b0e
[ 1.122785] KernelSU: GET_WRAPPER_FD = 0x40004b0f
[ 1.122788] KernelSU: MANAGE_MARK = 0xc0004b10
[ 1.122793] KernelSU: NUKE_EXT4_SYSFS = 0x40004b11
[ 1.122797] KernelSU: ADD_TRY_UMOUNT = 0x40004b12
[ 1.122800] KernelSU: GET_FULL_VERSION = 0x80004b64
[ 1.122804] KernelSU: GET_HOOK_TYPE = 0x80004b65
[ 1.122808] KernelSU: GET_ENABLE_KPM = 0x80004b66
[ 1.122812] KernelSU: SET_DYNAMIC_MANAGER = 0xc0004b67
[ 1.122815] KernelSU: GET_MANAGERS = 0xc0004b68
[ 1.122819] KernelSU: SET_ENABLE_UID_SCANNER = 0xc0004b69
[ 1.122823] KernelSU: MANUAL_SU = 0xc0004b6a
[ 1.122826] KernelSU: KPM_OPERATION = 0xc0004bc8
[ 1.122831] KernelSU: feature: registered handler for kernel_umount (id=1)
[ 1.122836] KernelSU: feature: registered handler for enhanced_security (id=2)
[ 1.122840] KernelSU: feature: registered handler for su_compat (id=0)
[ 2.016237] KernelSU: /init argc: 1
[ 2.180799] KernelSU: /init argc: 1
[ 2.284379] KernelSU: /init argc: 2
[ 2.284385] KernelSU: /init first arg: selinux_setup
[ 2.611609] KernelSU: /system/bin/init argc: 2
[ 2.611616] KernelSU: /system/bin/init first arg: second_stage
[ 2.611620] KernelSU: /system/bin/init second_stage executed
[ 2.646328] KernelSU: sid '81' is set for secctx_name 'u:r:priv_app:s0:c512,c768'
[ 2.646338] KernelSU: sid '82' is set for secctx_name 'u:r:init:s0'
[ 2.646342] KernelSU: sid '83' is set for secctx_name 'u:r:su:s0'
[ 2.646346] KernelSU: sid '84' is set for secctx_name 'u:r:zygote:s0'
[ 2.712321] KernelSU: hook_manager: unmark 427 exec /system/bin/init
[ 2.722826] KernelSU: vfs_read: /system/etc/init/atrace.rc, comm: init, count: 4096, rc_count: 336
[ 2.723099] KernelSU: read_iter_proxy append 3760 + 336
[ 2.723103] KernelSU: stop vfs_read_hook
[ 2.769979] KernelSU: hook_manager: unmark 428 exec /system/bin/ueventd
[ 2.779655] KernelSU: hook_manager: unmark 429 exec /system/bin/apexd
[ 3.200631] KernelSU: hook_manager: unmark 533 exec /apex/com.android.runtime/bin/linkerconfig
[ 3.281501] KernelSU: hook_manager: unmark 534 exec /vendor/bin/vendor_modprobe.sh
[ 3.358770] KernelSU: hook_manager: unmark 538 exec /vendor/bin/modprobe
[ 3.379095] KernelSU: hook_manager: unmark 539 exec /vendor/bin/init.qti.early_init.sh
[ 3.466869] KernelSU: hook_manager: unmark 543 exec /system/bin/prng_seeder
[ 3.467121] KernelSU: hook_manager: unmark 544 exec /vendor/bin/boringssl_self_test32
[ 3.535666] KernelSU: hook_manager: unmark 545 exec /vendor/bin/boringssl_self_test64
[ 3.550647] KernelSU: hook_manager: unmark 546 exec /vendor/bin/init.qti.qcv.sh
[ 3.634650] KernelSU: hook_manager: unmark 550 exec /system/bin/logd
[ 3.635432] KernelSU: hook_manager: unmark 551 exec /system/bin/lmkd
[ 3.638808] KernelSU: hook_manager: unmark 552 exec /system/bin/servicemanager
[ 3.643302] KernelSU: hook_manager: unmark 553 exec /system/system_ext/bin/hwservicemanager
[ 3.645888] KernelSU: hook_manager: unmark 554 exec /vendor/bin/vndservicemanager
[ 3.665729] KernelSU: hook_manager: unmark 558 exec /system/bin/boringssl_self_test32
[ 3.696350] KernelSU: hook_manager: unmark 559 exec /system/bin/boringssl_self_test64
[ 3.712313] KernelSU: hook_manager: unmark 563 exec /vendor/bin/hw/[email protected]
[ 3.715822] KernelSU: hook_manager: unmark 564 exec /vendor/bin/qseecomd
[ 3.720736] KernelSU: hook_manager: unmark 566 exec /vendor/bin/hw/[email protected]
[ 3.735719] KernelSU: hook_manager: unmark 567 exec /system/bin/vold
[ 3.770284] KernelSU: hook_manager: unmark 570 exec /system/bin/e2fsck
[ 3.836300] KernelSU: hook_manager: unmark 589 exec /system/bin/vdc
[ 3.855510] KernelSU: hook_manager: unmark 590 exec /system/bin/aconfigd-system
[ 3.921738] KernelSU: hook_manager: unmark 591 exec /system/bin/recovery-refresh
[ 3.925711] KernelSU: hook_manager: unmark 592 exec /system/bin/hw/android.system.suspend-service
[ 3.934672] KernelSU: hook_manager: unmark 593 exec /system/bin/keystore2
[ 3.935686] KernelSU: hook_manager: unmark 594 exec /vendor/bin/hw/android.hardware.boot-service.qti
[ 3.942272] KernelSU: hook_manager: unmark 595 exec /vendor/bin/hw/[email protected]
[ 3.951940] KernelSU: hook_manager: unmark 596 exec /vendor/bin/sscrpcd
[ 3.958163] KernelSU: hook_manager: unmark 600 exec /system/bin/vdc ... kernel no error</p>
设备信息：
- 设备：Redmi Note12 5G(sunstone)
- 操作系统版本：CrdA16
- KernelSU版本：40204
- 内核版本：5.4.300-qgki
附加信息：
<em>无响应</em>从日志中可以看出，KernelSU已经初始化，并且加载了驱动程序。但是，管理器报告说驱动程序没有被检测到。这可能是由多种原因引起的，例如驱动程序与当前内核版本不兼容、驱动程序配置错误或内核模块加载问题等。建议检查驱动程序的兼容性，并确保所有相关的配置都是正确的。如果问题仍然存在，可能需要进一步检查内核日志以获取更多详细信息。
评论已关闭