Hardened 3.13.2/gradm3.0*, can't find established /dev/grsec

[RickDeckard]

I've been having a bit of a problem here with grsecurity's RBAC system. Learning mode works to the extent that it spits out a default policy, I can input passwords to switch to different roles, and so forth. However, none of the policy takes hold and I can't set sysctl parameters such as grsec_lock. I believe the culprit is /dev/grsec itself, which I set via "mknod -m 622 /dev/grsec c 1 13" as advised to do before gradm can function at all. Any command passed to gradm other than -E or -D will display "The /dev/grsec device is not properly configured on your system or you are not using a grsec kernel."

The latter is, of course, false.

I've looked at the devices.txt file, searched Google, and checked wherever else I could for information. I've even tried every minor number from 10 to 30 on a hunch. This has been a persistent issue for me ever since gradm 2.9.1.

Is there something I'm overlooking or doing wrong?
_________________
The nine most dangerous words in the English language are "I'm from the government, and I'm here to help."