Hide boot on-screen errors, or get TV-out working on ATI Radeon X300
israeldahl at gmail.com
Sun Dec 7 20:30:31 UTC 2014
On 12/07/2014 01:31 PM, John Hupp wrote:
> I created /etc/sysctl.d/20-quiet-printk.conf with content:
> kernel.printk = 3 3 3 3
> I hit Return at the end, since an End-Of-Line character may be
> required to make the line effective.
> This overrides the default behavior established in
> /etc/sysctl.d/10-console-messages.conf with content:
> kernel.printk = 4 4 1 7
> The unwanted messages did not appear at the next boot (they are still
> available in /var/log/kern.log and syslog, however).
> I note that /etc/sysctrl.d/README instructs that 'service procps
> start' should be run after any changes, but this merely results in an
> output of 'unknown job: procps' and proved to be unnecessary anyway.
> The critical piece of instruction came from
> Though I was curious to know a bit more about the mechanisms in play,
> I didn't dig much further than that. I wondered, for instance, what
> behavior the default '4 4 1 7' specified, but never did find out. The
> files in sysctl.d are installed by procps (see the List of Files link
> at http://packages.ubuntu.com/trusty/admin/procps). And these, in
> turn, are part of the kernel configuration governed by sysctl (see
> Still looking for the meaning of '4 4 1 7' vs '3 3 3 3' I came to
> https://www.kernel.org/doc/Documentation/printk-formats.txt, but my
> eyes glazed over just skimming that, and I stopped there.
I will have to save this e-mail and look up that info. This is quite
informative to look at. I suppose I could create a startup script to
do something like: [making DATE=$(date -I) or whatever format ]
cp /var/log/kern.log ~/.kernlog-$DATE.log
Thanks for your research John!! You always seem to find the answer once
you start looking :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Lubuntu-users