-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
cybersnakeh edited this page Jan 15, 2026
·
2 revisions
Common issues and quick resolutions.
-
Module will not load
- Check kernel headers match the running kernel (
/lib/modules/$(uname -r)/build). - Inspect
dmesg | grep snakedrvfor errors (signing, symbol mismatches). - Ensure
modprobeorinsmodis executed as root.
- Check kernel headers match the running kernel (
-
/dev/snakedrvmissing- Reload udev:
udevadm control --reload-rules && udevadm trigger. - Verify the
snakeenginegroup exists; re-rundeploy.sh installto recreate rules.
- Reload udev:
-
Permission denied opening the device
- Add your user to
snakeengine:sudo usermod -aG snakeengine $USERthen re-login. - Check AppArmor/SELinux audit logs for denials.
- Add your user to
-
DKMS build failures
- Remove stale versions:
dkms remove -m snakedrv -v 1.0.0 --all. - Re-run
sudo ./deploy.sh install(or--no-dkmsto bypass). - Confirm
linux-headers-$(uname -r)are installed.
- Remove stale versions:
-
Secure Boot blocks loading
- Sign the module with
./sign-module.shand enroll the MOK. - Reboot and try
sudo ./deploy.sh loadagain.
- Sign the module with
-
No debug events or breakpoints not firing
- Ensure the watched address is mapped and matches the access size/type.
- DR slots are limited (4); clear existing breakpoints.
- Confirm the process is still attached and running.
-
Kernel panic or instability
- Develop in a VM or dedicated test host.
- Keep
debug_levelat 1; revert local modifications. - Validate against the shipping source and rebuild clean.