l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jan 17 17:19

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Network Configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Network Configuration

On Thu, 17 Jan 2002, Ken Bloom wrote:
> I didn't say I had a problem with my network card, I just said that
> `dmesg` didn't say anything about the card. Perhaps you missed it when
> I said that this ethernet card that `dmesg` didn't report was the one
> I was using to post my response to the list. So the question lies,
> what good is the `dmesg` test if it doesn't report a card I know to
> *is* working?

dmesg can report kernel boot information (including hardware
detection) unless your machine has been on a while , or something has been
logging stuff for dmesg to cause the older stuff to be wiped out.

You can think of the data available to dmesg as being limited for being
over-written as new data comes in. Immediately after a boot, assuming
other things are not complaining, dmesg should show you good detailed
information about your hardware.

Perhaps you have more wrong with your box. Check out 
# dmesg |more
and see what you have. 

A properly configured server which has been up for 175 days, has so little
reported for access with dmesg, that I can see to the top of where my
kernel was just starting to load. (And this is a busy web server.)

(Have had other servers with >300 days of uptime that also allow me to see
the top of my dmesg data from boot >300 days ago.

To have so quickly lost much of your kernel reported messages from your
dmesg output, suggest you may have some kernel problems, or maybe some
very verbose bits of code loaded in/by your kernel.

Sorry that I misunderstood the problem.

dmesg is very cool. When you system is well configured, you can have dmesg
called shortly after full boot to store your kernel boot info into a file
instead of trying to use your scroll back buffer for your tty and gdm to
copy and paste into a file, or copy by hand this data.

Also, it can help you to identify potential problems or a misconfigured
kernel or module. The man pages for it are short on my system, but
describe what it is for.


Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-----) C++$(++++) U++++$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++>++++ h(++)>+ r*>? z?
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!