dmesg outputs _NOTHING_

[Net Llama!]

On 02/28/2006 04:45 PM, David Bandel wrote:
> On 2/28/06, Net Llama! <netllama at linux-sxs.org> wrote:
>> I've gotten this system from a customer where running 'dmesg' returns
>> nothing at all.  I thought that perhaps they had built the kernel with a
>> zero size ring buffer, but even after putting a known good kernel on the
>> system, dmesg outputs nothing.  Anyone have any ideas?
>>
>> --
> 
> there is a way where a non-root user cannot see dmesg output.  CRS
> syndrome has clouded my memory.  Take a look at the klogd man page.  I
> believe I wrote about how to do this in my book (or maybe not, but it
> is possible to do this).  Something to do with empyting the ring
> buffer,  perhaps?

I'm seeing this problem as root.  'dmesg -c' will clear the ring buffer, 
but in my case the ring buffer is empty at boot up, and remains that way.

> 
> Look in /var/log/kern.log (or wherever /etc/syslog.conf logs kernel
> messages), they should still be there (the messages from the kernel).

nope, nothing gets logged there either.  and syslogd is running, and has 
the same configuration as other 'working' systems.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                       	       netllama at linux-sxs.org
LlamaLand		 		http://netllama.linux-sxs.org

  18:05:01 up 15:32,  1 user,  load average: 0.87, 0.51, 0.44