Note that there are a few issues here. The original problem, the error from setterm invocation, is likely rather a user-space problem, i.e. possibly some incorrect invocation. OTOH, another problem, the non-working blank despite of setterm command, is a kernel problem, and this strongly depends on the framebuffer driver (and KMS driver, too). This needs to be addressed in the kernel upstream.