Hi,
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
This hunk of the already metioned patch, which
modifies vt_console_print() in drivers/char/vt.c, is
possibly the cause:
@@ -2220,9 +2220,6 @@
}
set_cursor(vc);
- if (!oops_in_progress)
- poke_blanked_console();
-
quit:
clear_bit(0, &printing);
}
Is that new behaviour intentional?
The old behaviour looks more interesting to me,
allowing one to see console messages immediately even
if the console was blanked after some idle time.
Cheers,
Albert
[1]
http://marc.theaimsgroup.com/?l=linux-kernel&m=111052009232499&w=2
______________________________________________
Renovamos el Correo Yahoo!
Nuevos servicios, más seguridad
http://correo.yahoo.es
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |